Skip to content

chore(build): allow Maven release without GPG passphrase#30

Merged
bluestreak01 merged 1 commit into
mainfrom
optional-gpg-passphrase-release
May 21, 2026
Merged

chore(build): allow Maven release without GPG passphrase#30
bluestreak01 merged 1 commit into
mainfrom
optional-gpg-passphrase-release

Conversation

@sklarsa
Copy link
Copy Markdown
Contributor

@sklarsa sklarsa commented May 21, 2026

Summary

  • make MAVEN_GPG_PASSPHRASE optional for Maven Central releases
  • only add the gpg.passphrase Maven server entry when the secret value is present
  • keep existing AWS secret storage and password-protected key support unchanged

Testing

  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/maven_central_release.yml"); puts "workflow yaml ok"'
  • git diff --check
  • mvn -B -q -N -DforceStdout help:evaluate -Dexpression=project.version

@sklarsa sklarsa force-pushed the optional-gpg-passphrase-release branch from dc15ffb to 1751808 Compare May 21, 2026 16:52
@sklarsa sklarsa changed the title Allow Maven release without GPG passphrase chore(build): allow Maven release without GPG passphrase May 21, 2026
@bluestreak01 bluestreak01 merged commit b2ac9e5 into main May 21, 2026
11 checks passed
@bluestreak01 bluestreak01 deleted the optional-gpg-passphrase-release branch May 21, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants